Configuring Health Check Link Aggregation

To configure Health Check link aggregation you must first create a LAG. One port in the LAG serves as the logical port for the LAG and is the reference port used in configuration commands.

When you create the LAG, no monitoring is initially configured. The LAG is created in the same way that a static LAG is created and if no monitoring is ever created, this LAG behaves like a static LAG.

Create a LAG using:
enable sharing port grouping port_list {algorithm [address-based {L2 | L3 | L3_L4 | custom} | }]} {lacp | health-check}

The port you assign using the port parameter becomes the logical port for the link aggregation group and the LAG Group ID when using Health Check link aggregation. This logical port must also be included in the port list of the grouping itself.
Configure monitoring for each member port using:
configure sharing health-check member-port port add tcp-tracking IP Address {tcp-port TC Port frequency sec misses count}

If the TCP-port, frequency, or misses are not specified, the defaults described in the Switch Engine v33.1.1 Command Reference Guide are used.
Add the LAG to a VLAN whose subnet is the same as the configured tracking IP addresses.
configure vlan vlan add port lag port [tagged | untagged]

All of the tracking IP addresses must be in the same subnet in which the LAG belongs.
Note
VLANs to which Health Check LAG ports are to be added must be configured in loopback mode. This is to prevent the VLAN interface from going down if all ports are removed from the Health Check LAG. In a normal LAG when all ports are removed from the aggregator, the trunk is considered DOWN. As a consequence, if this were the only port in the VLAN, the VLAN interface would be brought DOWN as well. In the Health Check LAG situation, this would cause the TCP monitoring to fail because the L3 vlan interface used by TCP monitoring would no longer send or receive TCP data.